Skip to content

[release-v0.39] chore(deps): update grpc to v1.79.3#2690

Merged
theakshaypant merged 1 commit intotektoncd:release-v0.39.6from
theakshaypant:chore-update-deps
Apr 16, 2026
Merged

[release-v0.39] chore(deps): update grpc to v1.79.3#2690
theakshaypant merged 1 commit intotektoncd:release-v0.39.6from
theakshaypant:chore-update-deps

Conversation

@theakshaypant
Copy link
Copy Markdown
Member

@theakshaypant theakshaypant commented Apr 16, 2026

📝 Description of the Change

Upgrade google.golang.org/grpc to v1.79.3 to fix CVE-2026-33186 (GHSA-p77j-4mvh-x3m3), a critical HTTP/2 :path validation flaw that allows bypassing authorization rules in gRPC interceptors.

🔗 Linked GitHub Issue

N/A

🧪 Testing Strategy

  • Unit tests
  • Integration tests
  • End-to-end tests
  • Manual testing
  • Not Applicable

🤖 AI Assistance

AI assistance can be used for various tasks, such as code generation,
documentation, or testing.

Please indicate whether you have used AI assistance
for this PR and provide details if applicable.

  • I have not used any AI assistance for this PR.
  • I have used AI assistance for this PR.

Important

Slop will be simply rejected, if you are using AI assistance you need to make sure you
understand the code generated and that it meets the project's standards. you
need at least know how to run the code and deploy it (if needed). See
startpaac to make it easy
to deploy and test your code changes.

If the majority of the code in this PR was generated by an AI, please add a Co-authored-by trailer to your commit message.
For example:

Co-authored-by: Claude noreply@anthropic.com

✅ Submitter Checklist

  • 📝 My commit messages are clear, informative, and follow the project's How to write a git commit message guide. The Gitlint linter ensures in CI it's properly validated
  • ✨ I have ensured my commit message prefix (e.g., fix:, feat:) matches the "Type of Change" I selected above.
  • ♽ I have run make test and make lint locally to check for and fix any
    issues. For an efficient workflow, I have considered installing
    pre-commit and running pre-commit install to
    automate these checks.
  • 📖 I have added or updated documentation for any user-facing changes.
  • 🧪 I have added sufficient unit tests for my code changes.
  • 🎁 I have added end-to-end tests where feasible. See README for more details.
  • 🔎 I have addressed any CI test flakiness or provided a clear reason to bypass it.
  • If adding a provider feature, I have filled in the following and updated the provider documentation:
    • GitHub App
    • GitHub Webhook
    • Gitea/Forgejo
    • GitLab
    • Bitbucket Cloud
    • Bitbucket Data Center

Upgrade google.golang.org/grpc to v1.79.3 to fix
CVE-2026-33186 (GHSA-p77j-4mvh-x3m3), a critical HTTP/2
:path validation flaw that allows bypassing authorization
rules in gRPC interceptors.

Signed-off-by: Akshay Pant <akpant@redhat.com>
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates several Go dependencies in go.mod and go.sum, primarily focusing on golang.org/x packages, Google Cloud libraries, and gRPC. Feedback was provided regarding the update of github.com/go-jose/go-jose/v4, which is currently rendered ineffective by a replace directive pinning it to an older version.

Comment thread go.mod
github.com/fxamacker/cbor/v2 v2.9.0 // indirect
github.com/go-jose/go-jose/v3 v3.0.4 // indirect
github.com/go-jose/go-jose/v4 v4.1.2 // indirect
github.com/go-jose/go-jose/v4 v4.1.3 // indirect
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

high

The update of github.com/go-jose/go-jose/v4 to v4.1.3 is currently ineffective because it is being overridden by a replace directive at line 162, which pins the version to v4.0.5. Since this pull request is intended to update dependencies (likely for security or stability), you should update or remove the replace directive to allow the build to use the newer version. This ensures the dependency version is correct and that any security scanner alerts are properly addressed.

References
  1. Security scanner alerts may persist as false positives even after a dependency has been updated. When a bot flags a security issue that is believed to be resolved, confirm the dependency version is correct and investigate if the alert is a false positive before making further code changes.

@theakshaypant
Copy link
Copy Markdown
Member Author

Merging this as the deps update are same as the ones already done for 0.37 and 0.42

@theakshaypant theakshaypant marked this pull request as ready for review April 16, 2026 09:52
@theakshaypant
Copy link
Copy Markdown
Member Author

The go-testing lint failures are in unit test scripts and llm - which is a TP feature. Merging regardless of these failures.

* noctx: 9
* staticcheck: 2

@theakshaypant theakshaypant merged commit ff5b628 into tektoncd:release-v0.39.6 Apr 16, 2026
3 of 13 checks passed
@theakshaypant theakshaypant deleted the chore-update-deps branch April 16, 2026 10:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant